chore(deps): update all non-major dependencies #370
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.606.0
->3.609.0
3.606.0
->3.609.0
3.606.0
->3.609.0
3.606.0
->3.609.0
3.606.0
->3.609.0
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.4.2
->5.4.3
5.15.21
->5.16.0
5.15.21
->5.16.0
7.8.0
->7.9.0
0.1.3
->0.1.4
20.14.9
->20.14.10
7.14.1
->7.15.0
7.14.1
->7.15.0
2.147.2
->2.148.0
2.147.2
->2.148.0
2.1651.0
->2.1655.0
0.21.5
->0.23.0
10.4.2
->10.4.3
6.24.0
->6.24.1
5.5.2
->5.5.3
6.24.0
->6.24.1
5.3.2
->5.3.3
4.2.0
->4.2.1
🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-dynamodb)
v3.609.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
v3.609.0
Compare Source
Features
v3.608.0
Compare Source
Note: Version bump only for package @aws-sdk/client-s3
aws/aws-sdk-js-v3 (@aws-sdk/client-sesv2)
v3.609.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sesv2
v3.608.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sesv2
aws/aws-sdk-js-v3 (@aws-sdk/client-sfn)
v3.609.0
Compare Source
Note: Version bump only for package @aws-sdk/client-sfn
aws/aws-sdk-js-v3 (@aws-sdk/s3-request-presigner)
v3.609.0
Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.608.0
Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
middyjs/middy (@middy/core)
v5.4.3
Compare Source
What's Changed
ava
,swc
,c8
,lerna
, and moreNew Contributors
Full Changelog: middyjs/middy@5.4.2...5.4.3
mui/material-ui (@mui/icons-material)
v5.16.0
Compare Source
A big thanks to the 5 contributors who made this release possible. Here are some highlights ✨:
InitColorSchemeScript
for Next.js App Router (#42829) @siriwatknp@mui/material@5.16.0
InitColorSchemeScript
for Next.js App Router (#42829) @siriwatknpDefaultPropsProvider
(#42820) @siriwatknpCssVarsTheme
inresponsiveFontSizes
return type (@jxdp) (#42806) @jxdpgetInitColorSchemeScript
(#42838) @siriwatknpDocs
Core
All contributors of this release in alphabetical order: @aarongarciah, @alexey-kozlenkov, @jxdp, @oliviertassinari, @siriwatknp
mui/mui-x (@mui/x-date-pickers)
v7.9.0
Compare Source
Jul 5, 2024
We'd like to offer a big thanks to the 7 contributors who made this release possible. Here are some highlights ✨:
selectItem
andgetItemDOMElement
methods to the TreeView component public APIusePickersTranslations
hook public in the pickers componentData Grid
@mui/x-data-grid@7.9.0
pagination={undefined}
(#13349) @sai6855@mui/x-data-grid-pro@7.9.0
Same changes as in
@mui/x-data-grid@7.9.0
.@mui/x-data-grid-premium@7.9.0
Same changes as in
@mui/x-data-grid-pro@7.9.0
.Date and Time Pickers
@mui/x-date-pickers@7.9.0
usePickersTranslations
hook public (#13657) @flaviendelangle@mui/x-date-pickers-pro@7.9.0
Same changes as in
@mui/x-date-pickers@7.9.0
.Charts
@mui/x-charts@7.9.0
Zoom&Pan
to the Pro charts (unreleased) (#13405) @JCQuintasTree View
@mui/x-tree-view@7.9.0
selectItem
andgetItemDOMElement
methods to the public API (#13485) @flaviendelangleDocs
Core
react_next
workflow in CircleCI (#13360) @cherniavskiijscodeshift-add-imports
package (#13720) @LukasTy@mui/docs
usage (#13713) @LukasTytrautonen/cdk-dns-validated-certificate (@trautonen/cdk-dns-validated-certificate)
v0.1.4
Compare Source
0.1.4 (2024-07-02)
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.15.0
Compare Source
🚀 Features
eslint-plugin: [array-type] detect
Readonly<string[]>
caseeslint-plugin: back-port new rules around empty object types from v8
🩹 Fixes
disable
EXPERIMENTAL_useProjectService
indisabled-type-checked
shared configeslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any
eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.15.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
aws/aws-cdk (aws-cdk)
v2.148.0
Compare Source
Features
project.visibility
(#30103) (1bacb69)Bug Fixes
Reverts
delegatedZone
(#30440)" (#30606) (95280a0), closes #30600Alpha modules (2.148.0-alpha.0)
Features
Bug Fixes
v2.147.3
Compare Source
Bug Fixes
Alpha modules (2.147.3-alpha.0)
aws/aws-sdk-js (aws-sdk)
v2.1655.0
Compare Source
v2.1654.0
Compare Source
v2.1653.0
Compare Source
v2.1652.0
Compare Source
evanw/esbuild (esbuild)
v0.23.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.22.0
or~0.22.0
. See npm's documentation about semver for more information.Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made
--packages=external
the default behavior with--platform=node
. The default is now back to--packages=bundle
.I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
Fix preserving collapsed JSX whitespace (#3818)
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with
--jsx=preserve
. Here is an example:v0.22.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.21.0
or~0.21.0
. See npm's documentation about semver for more information.Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node
) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=external
to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node
(i.e. the previous behavior of--packages=external
is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundle
to allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundle
doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:
even when--packages=bundle
is present.The
--packages=
setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/
or.
or..
are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#
character) and TypeScript path remappings viapaths
and/orbaseUrl
intsconfig.json
(which are applied first).Drop support for older platforms (#3802)
This release drops support for the following operating systems:
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuild
npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasm
package and versions of node before node 17.4 (specifically thecrypto.getRandomValues
function).Update
await using
behavior to match TypeScriptTypeScript 5.5 subtly changes the way
await using
behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.Allow
es2024
as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/v
flag. With--target=es2024
, regular expressions that use the/v
flag will now be passed through untransformed instead of being transformed into a call tonew RegExp
.Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuild
npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by @ikmckenz.
Configuration
📅 Schedule: Branch creation - "before 6am on saturday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.